Setup Downtime Editor

Setup downtimes should be used to model situations where a location can process different types of entities, but needs to be setup to do so. Setup downtimes will not overlap but will preempt other downtimes in a manner similar to that of an entity. Setup downtimes are only available for single capacity locations.

Note that a setup downtime is assumed to occur only when an entity arrives at a location and is different from the previous entity to arrive at the location. Consequently, the word ALL in the prior entity field means all except the same entity type.

The Setup Downtime Editor consists of the edit table shown below. It contains fields for defining location downtimes based on the arrival of a new entity type.

Entity The incoming entity for which the setup occurs. If the setup time for all entity types is identical when shifting from the same prior entity, the reserved word ALL may be entered.

Prior Entity The entity preceding the entity for which the setup occurs. If the setup is the same regardless of the preceding entity, you may enter the reserved word ALL.

Logic Enter any logic statements to be processed when the downtime occurs. Click on the heading button to open a larger edit window.

Disable Select YES to temporarily disable the downtime without deleting it from the table.

This example shows that the time to setup Robot3 depends on the arriving entity and the prior entity. If a GearB follows a GearC, the setup time for the machine will be based on a Lognormal distribution with a mean of 4.5 minutes and a standard deviation of .95 min. But if a GearC follows a GearA, the setup time will be based on a Lognormal distribution with a mean of 2.3 min and a standard deviation of .2 min.